System and method of enabling audio conferencing in lieu of videoconferencing

ABSTRACT

An apparatus or method implemented in a computer system. In one embodiment the method includes receiving, from a device, a request to join a video call, and determining, in response to receiving the request, whether the device meets predetermined requirements to join the video call via videoconferencing. The method further includes sending, in response to determining the device does not meet the predetermined requirements to join the video call via videoconferencing, a message to the device, wherein the message comprises a link to join the call via audio conferencing.

TECHNICAL FIELD

This disclosure generally relates to video calls. In particular, thisdisclosure relates to an apparatus and method for joining a video callthrough audio conferencing when data connectivity problems may preventjoining the video call through video conferencing.

BACKGROUND

Video calls are a common way for people to meet as a group, but withoutbeing at the same physical location. Participants can be invited to avideo call, and join from their computers or smartphones. Video callsenable participants to see and hear each other, and largely converse asthey would during an in-person group meeting.

Video calls are particularly useful for healthcare providers (e.g.,doctors, nurses, etc.) and patients. Prior to video calls patientsvisited health care facilities (e.g., hospitals, clinics, etc.) toreceive health related services. With video calls, patients can consultwith healthcare providers in the comfort of their own homes.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments and implementations of the present disclosure will beunderstood more fully from the detailed description given below and fromthe accompanying drawings of various aspects and implementations of thedisclosure, which, however, should not be taken to limit the disclosureto the specific embodiments or implementations, but are for explanationand understanding only.

FIG. 1 is a diagram illustrating an example network architecture inaccordance with one or more embodiments of the disclosure.

FIG. 2 is a flow diagram of an example process of setting up a videocall in accordance with one or more embodiments of the disclosure.

FIG. 3 is a diagram illustrating an example patient interface inaccordance with one or more embodiments of the disclosure.

FIG. 4 is a flow diagram illustrating an example process for evaluatingdata connectivity between a patient computing device and a video callserver in accordance with one or more embodiments of the disclosure.

FIG. 5 is a flow diagram of an example process of setting up a telephonecall in accordance with one or more embodiments of the disclosure.

FIG. 6 is a diagram illustrating an example patient interface inaccordance with one or more embodiments of the disclosure.

FIG. 7 is a block diagram of an example apparatus that may perform oneor more of the operations described herein, in accordance with someembodiments of the present disclosure.

DETAILED DESCRIPTION

Patients can visit with health care providers through video calls ifsufficient data connectivity exits between their computing devices andservers that host video calls. If data connectivity is not sufficient, apatient can still join the video call through audio conferencing, whichenables audio communication between the health care provider and thepatient through, for example, mobile phones or voice over internetprotocol (VOIP).

Sufficient data connectivity between patient computing devices and videocall servers depends on several variables. For example, the settings ofthe software (e.g., browser and/or mobile video call application)executing on a patient's computing device (e.g., smartphone or computer)should be compatible with the requirements of the video server that ishosting the video call. The patient's computing device may lack theprocessing bandwidth to support a video call, or the network connectionto the patient's smartphone or computer may not be strong enough tosupport the video call. Any one of these factors can lead toinsufficient data connectivity between the video call server and thepatient's computing device. Some patients may not be proficient in theuse of computing devices to correct problems that inhibit video callswhile they are communicating with their provider.

The present disclosure presents a method and apparatus for detectingdata connectivity problems with a patient's computing device. Thepresent disclosure also presents a method and apparatus for placing anaudio-only telephone call to the patient when data connectivity problemsare detected. While the telephone call does not provide videocommunication, the telephone call enables audio communication betweenthe patient and the healthcare provider.

FIG. 1 is a diagram illustrating an example network architecture 100, inaccordance with one or more embodiments of the disclosure. The networkarchitecture 100 has a network 105 that includes the Internet, anauthentication server 110, a messaging server 120, a video server 130, apatient 141, patient computing devices 142, a healthcare provider 151,healthcare computing devices 152, a service provider 161, and serviceprovider computing devices 162. Examples of computing devices mayinclude, but are not limited to, smartphones, tablet computers, laptopcomputers, desktop computers, etc. In the illustrated example, patientcomputing devices 142 include smart phone 142-1, laptop computer 142-2,and desktop computer 142-3. Healthcare provider computing devices 152include smart phone 152-1, laptop computer 152-2, and desktop computer152-3. Service provider computing devices include smart phone 162-1,laptop computer 162-2, and desktop computer 162-3.

Healthcare provider 151 may be a person who provides health relatedservices to patient 141. Examples of healthcare providers may include,but are not limited to, doctors, pharmacists, dentists, nurses,therapists, psychologists, technicians, surgeons, etc. Healthcareprovider 151 may use any of computing devices 152 to communicate withpatient 141 and service provider 161 through a video call hosted onvideo server 130.

Service provider 161 may provide additional or ancillary services topatient 141. Examples of service providers may include, but are notlimited to, insurance providers, translators (e.g., languagetranslators), billing specialists, etc. Service provider 161 may use anyof the computing devices 162 to communicate with patient 141 andhealthcare provider 151 via the video call.

Patient 141 may use smart phone 142-1, computer 142-2 or computer 142-3to communicate with healthcare provider 151 and service provider 161 viaa video call hosted on the video call server 130, but only if sufficientdata connectivity can be established between the computing device 142and video server 130. Insufficient data connectivity may prevent thevideo call. Insufficient data connectivity may stem from, for example,settings or software on patient's computing device 142 that are notcompatible with the requirements of the video call. A weak networkconnection to patient computing device 142 may also prevent the videocall. Other factors may adversely affect the video call.

Authentication server 110 may authenticate healthcare provider 151,service provider 161, and/or patient 141. Messaging server 120 can sendmessages to computing devices such as patient computing devices 142.These messages may include links to video calls hosted by video server130 or links to join video calls via audio conferencing only. Inaddition to hosting video calls, video server 130 can assess dataconnectivity to computing devices including any of the patient computingdevices 142. More particularly, video server 130 can send test messagesto patient computing devices 142, which are designed to gatherinformation about software executing on the computing devices, usersettings on the computing devices, processing bandwidth of the computingdevices, data transmission bandwidth to the computing devices, etc.Video server 130 can evaluate the data connectivity between video server130 and patient computing device 142 based on the information it gathersfrom responses to the test messages. Video server 130 can host a videocall between patient 141, healthcare provider 151, and service provider160 that involves an exchange of audio and video data with computingdevice 142 assuming sufficient data connectivity.

System architecture 100 allows healthcare provider 151 to set up a videocall, which involves sending patient computing device 142 a video calllink that can be activated by patient 141. This link allows patient 141to join a video call with healthcare provider 151, assuming sufficientdata connectivity exits between video server 130 and the patient'scomputing device 142. FIG. 2 illustrates relevant aspects of a processfor setting up a video call with patient 141. This process starts afterhealthcare provider 151 launches an app (e.g., an application, aprogram, etc.) on one of the healthcare provider's computing device 152.The app allows the healthcare provider 151 to set up a video call withpatient 141. The app communicates with the video server 130, which inturn communicates with the messaging server 120. The app prompts thehealthcare provider 151 for information related to the video call thatmay include: the health provider's name, the health provider's telephonenumber, the patient's name, the patient's telephone number for smartphone 142-1, the patient's email address for computer 142-2 or 142-3,etc. The video call information is received by video server 130 at step202. At step 204 video server 130 stores the information in video-callinformation memory. Rather than using an app executing on healthcareprovider's computing device 152, in an alternative embodiment,healthcare provider 151 can set up a video call with patient through abrowser executing computing device 152.

The video server 130 configures the video call (also known as a virtualconference room) on video server 130. Configuration includes generatinga unique identifier for the video call as shown in step 206. Video callserver 130 also generates a link to the video call. The link may includeaccess information for the video call, including the video callidentifier generated in stop 206. In step 210 video server 130 maps theidentifier generated in step 206 to the video call information that wasstored in video-call information memory at step 204.

Video server 130 is in data communication with messaging server 120.Messaging server 120 receives video call configuration information fromvideo server 130 including the link generated by video server 130 forthe example video call, and other information related to the video callsuch as a telephone number for smart phone 142-1, email address forlaptop computer 142-2, etc. The messaging server 120 sends a message topatient computing device 142 with the link generated by video server 130in step 214. For example, the messaging server 120 may send a shortmessage service (SMS) message with the link to patient smartphone 142-1,or messaging server 120 may send an email with the link to patientlaptop computer 142-2, or both.

FIG. 3 is a diagram illustrating an example patient interface 300displayed on patient device 142 when patient 141 opens the message sentby messaging server 120. Interface 300 displays example message 305received from messaging server 120. The message 305 may indicate in textthat healthcare provider 151 wants to initiate a video call with patient141. The message 305 includes example link 310 and additional text 320.The additional text 320 may convey additional information related to thevideo call, such as the identity of the healthcare provider who isinitiating the video call (e.g., a name of the healthcare provider 151),when the video call is scheduled to occur, the purpose of the video call(e.g., a checkup, a follow-up consultation, etc.). In one embodiment,the link 310 may be a uniform resources locator (URL). Although thepresent disclosure refers to a URL, other types of resource locators,identifiers, resource identifiers, etc., may be use in otherembodiments.

The “https://” portion of the link 310 may indicate the communicationprotocol for the video call. For example, the “https://” portionindicates that a Hypertext Transfer Protocol (HTTP) communicationchannel along with transport layer security (TLS) is be used to join andsupport the video call over network 105.

The “visit.doximity.com” portion of the link 310 indicates a location312 in the network for the video server 130 that hosts the video call.Different locations (e.g., different domain names) may be used toidentify and locate different video servers. In some examples, the linkmay also include an indication of a path to route video data for thevideo call.

In one embodiment, the portion “tw1-4cw-eyp” of the link 310 may be theidentifier 314 that is unique to the video call, which was generated instep 206 of FIG. 2 . The identifier 214 should be unique within thedomain name and/or video server 130. Identifier 314 should be linked tothe video call information that is stored in video-call informationmemory, which can be accessible by servers 110, 120, 130, or 140. Theformat of the identifier 314 may vary in different embodiments. The “?”portion of the link 310 may be a separator between different portions ofthe link 210.

In one embodiment, the “e=qpOnco” portion of the of the link 310 mayindicate or represent, a time or time period 316 for the video call. Forexample, the “e=qpOnco” portion may indicate a start time for the videocall (e.g., a time when video call should start). In another example,the “e=qpOnco” portion may indicate a time frame in which the video callshould occur (e.g., may indicate a start time and an end time for thevideo call). In a further example, the “e=qpOnco” portion may indicatean expiration time (e.g., a latest time) within which the patient isable to join or setup the video call.

The “e=qpOnco&s=q45” portion of the of the link 310 may be a signature218 to help increase the security of the video call. The“e=qpOnco&s=q45” portion may prevent a malicious person from modifyingthe link 310. If the link 310 has been modified by the malicious user,the video server will reject the request to join or setup the video callif the signature does not match the signature obtained by the videoserver. The “e=qpOnco&s=q45” portion may also prevent unauthorized usersfrom joining the video call. For example, the “e=qpOnco&s=q45” portionmay be generated using various encryption and/or hashing algorithms. Inone embodiment, the “e=qpOnco&s=q45” portion may be generated by hashingthe previous portions of the link 310 using a hash-based messageauthentication code secure hash algorithm (HMAC-SHA). This may prevent amalicious person from guessing the signature in an attempt to join thevideo call.

Patient 141 can join the video call with healthcare provider 151 byactivating link 310. Assuming sufficient data connectivity withpatient's computing device 142, the video call may proceed with anexchange of data (e.g., video data, video frames, audio data, audioframes, etc.) between patient computing device 142 and healthcareprovider computing device 152 via video server 120. Without sufficientdata connectivity the video call might not proceed. When patient 141activates link 310, a process can be implemented for evaluating dataconnectivity before starting the video call.

FIG. 4 illustrates relevant aspects of an example process for assessingdata connectivity in accordance with one aspect of the presentdisclosure. This process begins after patient 141 activates link 310,which prompts patient computing device 142 to send a request to videocall server 130 to join the video call. In step 402 video server 130receives the request from patient computing device 142 to join the videocall.

A determination can be made as to whether the patient computing device142 meets predetermined requirements to join the video call viavideoconferencing. The determination can be made by the patientcomputing device 142, the video call server 130, by the patientcomputing device 142 acting in concert with the video call server 130,or by another device. For example, patient computing device 142 may sendone or more messages for testing data connectivity to video server 130as shown in step 404.

In an embodiment, patient computing device 142 may send a ping messagethat assesses the network path between video service 130 and computingdevice 142. Ping messages measure the round-trip time for messages sentfrom the source to a destination that are echoed back to the source. Theround-trip time for the ping sent by computing device 142 can be used toassess the bandwidth of the network connection, and whether it cansupport the video call.

Patient computing device 142 may send a trace route message towardsvideo call server 130. A traceroute can be used to track in real-timethe pathway taken by a packet on network 105 from patient computingdevice 142 to video server 130, reporting the IP addresses of all therouters in between. Traceroute can also record the time taken for eachhop the packet makes during its route to video call server 130.

Patient computing device 142 may send a message to test variations indata packet transmission delay to video call server 130, or the numberof data packets that do not reach video call server 130 in a given timeperiod.

In an embodiment, patient computing device 142 can send test messages todetermine whether a firewall or virtual private network exists in thedata communication path between video server 130 and patient computingdevice 142.

In step 406 patient computing device 142 can receive one or moreresponses from to the one or more test messages, respectively, that weresent in step 404. Patient computing device 142 can process datacontained within the test messages and/or responses to determine whetherthe patient computing device 142 meets predetermined requirements tojoin the video call via videoconferencing. More particularly, thepatient computing device 142 can determine whether the patient'scomputing device 142 can support a video call with video server 130 asshown in step 410. For example, the echo round-trip time to traversenetwork 105 from patient computing device 142 to video call server 130and back, as identified in a ping message response, is compared to apredetermined threshold time value that is required to support a videocall. Information received in other test message responses can also beprocessed to evaluate data connectivity between video call server 130and patient computing device 142. In response to a determination thatadequate connectivity exists the video call is started in step 414. Inaddition to the test messages, patient computing device 142 candetermine if its browser and its version is compatible with video server130. For example, the browser software available in patient computingdevice 142, is compared by patient computing device 142 to one or morebrowsers that are required by video server 130 to support a video call.

In response to a determination that patient computing device 142 doesnot meet the predetermined requirements, and the video call to patientcomputing device 142 cannot be supported, patient computing device 142can initiate a process to place a telephone from the video server topatient smart phone 142-1 as shown in step 416. FIG. 5 illustratesrelevant aspects of a process for implementing step 416. At step 502,video call server 130 prompts messaging server 120 to generate and senda “call-me” message (e.g., an SMS message, a MMS message, a chatmessage, a text message, an email message, etc.) to patient's computingdevice 142. This message contains one or more links and text for displayby patient computing device 142.

FIG. 6 illustrates an example patient interface 600 displayed on patientdevice 142 when patient 141 opens the message sent by messaging server120 in step 502. Interface 600 displays an example call-me message 605received from messaging server 120. The message 605 may include a textmessage 606 indicating weak data connectivity to patient computingdevice 142 has been detected. Another text message may indicate afirewall in the communication path between server 130 and computingdevice 142 may prevent the video call. Other text messages arecontemplated.

Message 605 includes first and second links 602 and 604, respectively.First link 602 may be the same or similar link 310 that was provided inthe message 305 of FIG. 3 , which was previously displayed on patient'scomputing device 142. Text 606 can be positioned next to link 602, whichindicates weak data connectivity and a suggestion (e.g., “try closingapps”) for improving data connectivity. Link 602, when activated bypatient 141, will reinitiate the process shown within FIG. 5 . Thesecond link 604 may be a URL, although other links are contemplated.Like link 305 shown in FIG. 3 , the “visit.doximity.com” portion of thelink 604 indicates the location for the video server 130. The portion“tw1-4cw-eyp” of the link 604 should be the same identifier shown inFIG. 3 , which is unique to the video call and generated in step 206 ofFIG. 2 . The “e=spcp” portion of the of the link 604 may indicate orrepresent an instruction to initiate a phone call. The “e=qpOnco&s=q45”portion of the of the link 604 may be the same signature in link 305shown in FIG. 3 , which helps increase the security of the video call.This may prevent a malicious person from guessing the signature in anattempt to join the video call.

Patient 141 can optionally activate link 604, and in response patientcomputing device 142 sends a request message to video server 130. Thismessage should include the video call identifier “tw1-4cw-eyp” and theportion “e=spcp” from link 604 that represents instruction to initiate aphone call. In step 504 video server receives the message generated andsent in step 502. In response, as shown in step 506, video server 130access video-call information memory to read healthcare provider 151'sphone number and patient 141's phone number for smart phone 142-1, whichis mapped to video call identifier “tw1-4cw-eyp.” Video call server 130can then place a phone call to, for example, patient smartphone 142-1 instep 510. When patient 142 answers the phone call using smartphone142-1, an audio-only communication channel (e.g., a cellular telephonechannel) is established between smart phone 142-1 and the video callserver 130. The established audio-only communication channel enablesaudio conferencing between patient 141 to visit with healthcare provider151. Video server 130 can set up an alternative communication channel instep 510. For example, instead of placing a call to patient smartphone141-2, video server 130 can place a VOIP call to a patient computingdevice 142-2 or 142-3 in step 510. Or video server 130 can set up textmessaging with video server 130 in step 510.

FIG. 7 is a block diagram of an example data processing device 700 thatmay perform one or more of the operations described herein, inaccordance with some embodiments. Data processing device 700 may beconnected to other data processing devices in a LAN, an intranet, anextranet, and/or the Internet. The data processing device may operate inthe capacity of a server machine in the client-server networkenvironment or in the capacity of a client in a peer-to-peer networkenvironment. The data processing device may be provided by a personalcomputer (PC), a set-top box (STB), a server, a network router, switchor bridge, or any machine capable of executing a set of instructions(sequential or otherwise) that specify actions to be taken by thatmachine. Further, while only a single data processing device isillustrated, the term “data processing device” shall also be taken toinclude any collection of data processing devices that individually orjointly execute a set (or multiple sets) of instructions to perform themethods discussed herein.

The example data processing device 700 may include a processing unit(e.g., a general purpose processor, a PLD, etc.) 702, a main memory 704(e.g., synchronous dynamic random access memory (DRAM), read-only memory(ROM)), a static memory 706 (e.g., flash memory and a data storagedevice 718), which may communicate with each other via a bus 730.

Processing unit 702 may be provided by one or more general-purposeprocessing devices such as a microprocessor, central processing unit, orthe like. In an illustrative example, processing unit 702 may comprise acomplex instruction set computing (CISC) microprocessor, reducedinstruction set computing (RISC) microprocessor, very long instructionword (VLIW) microprocessor, or a processor implementing otherinstruction sets or processors implementing a combination of instructionsets. Processing unit 702 may also comprise one or more special-purposeprocessing devices such as an application specific integrated circuit(ASIC), a field programmable gate array (FPGA), a digital signalprocessor (DSP), network processor, or the like. The processing unit 702may be configured to execute the operations described herein, inaccordance with one or more aspects of the present disclosure, forperforming the operations and steps discussed herein.

Data processing device 700 may further include a network interfacedevice 708 which may communicate with a network 720. The data processingdevice 700 also may include a video display unit 710 (e.g., a liquidcrystal display (LCD) or a cathode ray tube (CRT)), an alphanumericinput device 712 (e.g., a keyboard), a cursor control device 714 (e.g.,a mouse) and an acoustic signal generation device 716 (e.g., a speaker).In one embodiment, video display unit 710, alphanumeric input device712, and cursor control device 714 may be combined into a singlecomponent or device (e.g., an LCD touch screen).

Data storage device 718 may include a computer-readable storage medium728 on which may be stored one or more sets of instructions 725 that mayinclude instructions for carrying out the operations described herein,in accordance with one or more aspects of the present disclosure.Instructions 725 may also reside, completely or at least partially,within main memory 704 and/or within processing unit 702 duringexecution thereof by data processing device 700, main memory 704 andprocessing unit 702 also constituting computer-readable media. Theinstructions 725 may further be transmitted or received over a network720 via network interface device 708.

While computer-readable storage medium 728 is shown in an illustrativeexample to be a single medium, the term “computer-readable storagemedium” should be taken to include a single medium or multiple media(e.g., a centralized or distributed database and/or associated cachesand servers) that store the one or more sets of instructions. The term“computer-readable storage medium” shall also be taken to include anymedium that is capable of storing, encoding or carrying a set ofinstructions for execution by the machine and that cause the machine toperform the methods described herein. The term “computer-readablestorage medium” shall accordingly be taken to include, but not belimited to, solid-state memories, optical media and magnetic media.

The foregoing description, for the purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the embodiments and its practical applications, to therebyenable others skilled in the art to best utilize the embodiments andvarious modifications as may be suited to the particular usecontemplated. Accordingly, the present embodiments are to be consideredas illustrative and not restrictive, and the invention is not to belimited to the details given herein, but may be modified within thescope and equivalents of the appended claims.

What is claimed is:
 1. A method, comprising: receiving, from a device, arequest to join a video call; determining, in response to receiving therequest, whether the device meets predetermined requirements to join thevideo call via videoconferencing; and sending, in response todetermining the device does not meet the predetermined requirements tojoin the video call via videoconferencing, a message to the device,wherein the message comprises a link to join the video call via audioconferencing.
 2. The method of claim 1, wherein the message includes ashort message service (SMS) message comprising the link to join thevideo call via audio conferencing.
 3. The method of claim 1 furthercomprising: receiving a request to join the video call via audioconferencing only in response to sending the message to the device; andinitiating the telephone call in response to receiving the request tojoin the video call via audio conferencing.
 4. The method of claim 3wherein the telephone call is a voice over internet protocol (VOIP)telephone call.
 5. The method of claim 1 wherein the determining whetherthe device meets the predetermined requirements includes sending anetwork ping message, and receiving a network ping response message. 6.The method of claim 5: wherein the network ping response messagecomprises an echo round-trip time; wherein determining whether thedevice meets the predetermined requirements comprises comparing the echoround-trip time with a threshold value.
 7. The method of claim 1 whereinthe determining whether the device meets the predetermined requirementsincludes identifying a browser executing on the device.
 8. The method ofclaim 7 wherein the determining whether the device meets thepredetermined requirements comprises determining the browser executingon the device is incompatible with the video call via videoconferencing.
 9. The method of claim 1 wherein the determining whetherthe device meets the predetermined requirements includes determiningwhether a network firewall exists in a communication path to the device.10. The method of claim 3 further comprising: storing a telephone numberin memory before receiving, from the device, the request to join thevideo call; in response to the receiving the request to join the videocall via audio conferencing, access the memory to read the telephonenumber; and wherein the telephone call is initiated using the telephoneread from memory.
 11. A non-transitory computer-readable medium storinginstructions that, when executed by one or more processors of a system,cause the system to perform a method comprising: receiving, from adevice, a request to join a video call; determining, in response toreceiving the request, whether the device meets predeterminedrequirements to join the video call via videoconferencing; and sending,in response to determining the device does not meet the predeterminedrequirements to join the video call via videoconferencing, a message tothe device, wherein the message comprises a link to join the video callvia audio conferencing.
 12. The non-transitory computer-readable mediumof claim 11, wherein the message includes a short message service (SMS)message comprising the link to join the video call via audioconferencing.
 13. The non-transitory computer-readable medium of claim12 wherein the method comprises: receiving a request to join the videocall via audio conferencing in response to sending the message to thedevice; and initiating the telephone call in response to receiving therequest to join the video call via audio conferencing.
 14. Thenon-transitory computer-readable medium of claim 11 wherein thecomputing device is the smartphone.
 15. The non-transitorycomputer-readable medium of claim 12 wherein the determining whether thedevice meets the predetermined requirements includes sending a networkping message, and receiving a network ping response message.
 16. Thenon-transitory computer-readable medium of claim 13: wherein the networkping response message comprises an echo round-trip time; wherein thedetermining whether the device meets the predetermined requirementscomprises comparing the echo round-trip time with a threshold value. 17.The non-transitory computer-readable medium of claim 12 wherein thedetermining whether the device meets the predetermined requirementsincludes identifying a browser executing on the device.
 18. Thenon-transitory computer-readable medium of claim 15 wherein thedetermining whether the device meets the predetermined requirementscomprises determining the browser executing on the device isincompatible with the video call via video conferencing.
 19. A systemcomprising: a memory configured to store a telephone number; and one ormore processors configured to receive, from a device, a request to joina video call; determine, in response to receiving the request, whetherthe device meets predetermined requirements to join the video call viavideoconferencing; and send, in response to determining the device doesnot meet the predetermined requirements to join the video call viavideoconferencing, a message to the device, wherein the messagecomprises a link to join the video call via audio conferencing.
 20. Thesystem of claim 19 wherein the one or more processors are furtherconfigured to: receive a request to join the video call via audioconferencing in response to sending the message to the device; andinitiate the telephone call in response to receiving the request to jointhe video call via audio conferencing.